The remote Redhat Enterprise Linux 7 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - libgit2: NTFS protections inactive when running Git in the Windows Subsystem for Linux (CVE-2020-12279)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

The remote Redhat Enterprise Linux 8 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - libgit2: NTFS protections inactive when running Git in the Windows Subsystem for Linux (CVE-2020-12279)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

The remote Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 23.10 host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6678-1 advisory.

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. checkout.c mishandles equivalent     filenames that exist because of NTFS short names. This may allow remote code execution when cloning a     repository. This issue is similar to CVE-2019-1353. (CVE-2020-12279)

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

  - libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid     API, allowing to build Git functionality into your application. Using well-crafted inputs to     `git_revparse_single` can cause the function to enter an infinite loop, potentially causing a Denial of     Service attack in the calling application. The revparse function in `src/libgit2/revparse.c` uses a loop     to parse the user-provided spec string. There is an edge-case during parsing that allows a bad actor to     force the loop conditions to access arbitrary memory. Potentially, this could also leak memory if the     extracted rev spec is reflected back to the attacker. As such, libgit2 versions before 1.4.0 are not     affected. Users should upgrade to version 1.6.5 or 1.7.2. (CVE-2024-24575)

  - libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid     API, allowing to build Git functionality into your application. Using well-crafted inputs to     `git_index_add` can cause heap corruption that could be leveraged for arbitrary code execution. There is     an issue in the `has_dir_name` function in `src/libgit2/index.c`, which frees an entry that should not be     freed. The freed entry is later used and overwritten with potentially bad actor-controlled data leading to     controlled heap corruption. Depending on the application that uses libgit2, this could lead to arbitrary     code execution. This issue has been patched in version 1.6.5 and 1.7.2. (CVE-2024-24577)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-2936 advisory.

  - A flaw was found in libgit2 before version 0.27.3. It has been discovered that an unexpected sign     extension in git_delta_apply function in delta.c file may lead to an integer overflow which in turn leads     to an out of bound read, allowing to read before the base object. An attacker may use this flaw to leak     memory addresses or cause a Denial of Service. (CVE-2018-10887)

  - A flaw was found in libgit2 before version 0.27.3. A missing check in git_delta_apply function in delta.c     file, may lead to an out-of-bound read while reading a binary delta file. An attacker may use this flaw to     cause a Denial of Service. (CVE-2018-10888)

  - In ng_pkt in transports/smart_pkt.c in libgit2 before 0.26.6 and 0.27.x before 0.27.4, a remote attacker     can send a crafted smart-protocol ng packet that lacks a '\0' byte to trigger an out-of-bounds read that     leads to DoS. (CVE-2018-15501)

  - Integer overflow in the index.c:read_entry() function while decompressing a compressed prefix length in     libgit2 before v0.26.2 allows an attacker to cause a denial of service (out-of-bounds read) via a crafted     repository index file. (CVE-2018-8098)

  - Incorrect returning of an error code in the index.c:read_entry() function leads to a double free in     libgit2 before v0.26.2, which allows an attacker to cause a denial of service via a crafted repository     index file. (CVE-2018-8099)

  - A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka     'Git for Visual Studio Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1349,     CVE-2019-1350, CVE-2019-1354, CVE-2019-1387. (CVE-2019-1352)

  - An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3,     v2.16.6, v2.15.4, and v2.14.6. When running Git in the Windows Subsystem for Linux (also known as WSL)     while accessing a working directory on a regular Windows drive, none of the NTFS protections were active.
    (CVE-2019-1353)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. checkout.c mishandles equivalent     filenames that exist because of NTFS short names. This may allow remote code execution when cloning a     repository. This issue is similar to CVE-2019-1353. (CVE-2020-12279)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

According to the versions of the libgit2 package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - An issue was discovered in libgit2 before 0.28.4 and     0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data     Streams. This may allow remote code execution when     cloning a repository. This issue is similar to     CVE-2019-1352.(CVE-2020-12278)

  - An issue was discovered in libgit2 before 0.28.4 and     0.9x before 0.99.0. checkout.c mishandles equivalent     filenames that exist because of NTFS short names. This     may allow remote code execution when cloning a     repository. This issue is similar to     CVE-2019-1353.(CVE-2020-12279)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3340 advisory.

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. checkout.c mishandles equivalent     filenames that exist because of NTFS short names. This may allow remote code execution when cloning a     repository. This issue is similar to CVE-2019-1353. (CVE-2020-12279)

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
195757	RHEL 7 : libgit2 (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	5/11/2024	5/11/2024	critical
195732	RHEL 8 : libgit2 (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	5/11/2024	5/11/2024	critical
191559	Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 23.10 : libgit2 vulnerabilities (USN-6678-1)	Nessus	Ubuntu Local Security Checks	3/5/2024	3/6/2024	critical
159090	Debian DLA-2936-1 : libgit2 - LTS security update	Nessus	Debian Local Security Checks	3/21/2022	11/3/2023	critical
139964	EulerOS 2.0 SP8 : libgit2 (EulerOS-SA-2020-1861)	Nessus	Huawei Local Security Checks	8/28/2020	2/22/2024	critical
171871	Debian DLA-3340-1 : libgit2 - LTS security update	Nessus	Debian Local Security Checks	2/24/2023	2/24/2023	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical